Summary

Xiaomi MiMo API requires reasoning_content in follow-up requests when tool calls exist in conversation histo
ry. Forge's pipeline already handles this for DeepSeek, Fireworks, and Kimi via the ReasoningContent + DefaultReasoningContent transformers, but Xiaomi MiMo was left out, causing tool-based conversations to fail after the first tool call.

Fix

Three changes in crates/forge_app/src/dto/openai/transformers/pipeline.rs:

1. ReasoningContent guard — added is_xiaomi_mimo_provider(provider) so that reasoning_details are converted to reasoning_content for MiMo, matching DeepSeek/Fireworks/Kimi behavior.

2. DefaultReasoningContent guard — added the same check so that assistant messages without reasoning still get an empty reasoning_content field, which MiMo requires when tool calls are present.

3. New helper — extracted is_xiaomi_mimo_provider() following the existing is_deepseek_provider() / is_zai_provider() pattern.

Testing

Two new tests added (mirroring existing DeepSeek tests):

• test_xiaomi_mimo_provider_converts_reasoning_details_to_reasoning_content — reasoning_details → reasoning_content conversion
• test_xiaomi_mimo_provider_falls_back_to_empty_reasoning_content_when_none — verifies empty fallback when no reasoning is present

Full test suite: 702 passed, 0 failed. Clippy and fmt clean.

Related

• Fixes #[3347]